|
DNS management software is computer software that controls Domain Name System (DNS) server clusters. DNS data is typically deployed on multiple physical servers. The main purposes of DNS management software are: *to reduce human error when editing complex and repetitive DNS data *to reduce the effort required to edit DNS data *to validate DNS data ''before'' it is published to the DNS servers *to automate the distribution of DNS data ==Background== In 1995, there were only 70,000 domains in existence.〔(【引用サイトリンク】url=http://ftp.isc.org/www/survey/reports/1995/07/report.html )〕 The way to register them was by email and the way to publish them was BIND. By mid-1997, the domain count was 1.3 million.〔(【引用サイトリンク】url=http://ftp.isc.org/www/survey/reports/1997/07/report.html )〕 As the number of domains and (internet hosts skyrocketed ), so too did the quantity of DNS data and the time required to manage it. Sysadmins responded by writing Perl or Shell scripts that helped automate DNS changes. These scripts were mostly in-house tools. The closest thing to widely available DNS management software was the BIND module in webmin, which provided web tools for editing BIND zone files. During the late 90's, the sheer quantity of DNS data was overwhelming the tools available to manage it. The cost of managing the data instigated the birth of DNS management software. The costs can best be explained by illustration. In 1998, three of the largest web hosting companies (HostPro, Interland, and Vservers) each hosted about 100,000 DNS zones. DNS changes were made by telnetting to a BIND master and editing zone files with a text editor. A staff of several DNS admins performed this task all day, every day. Their changes would only take effect after a BIND reload. Because disks were slow, it took several hours for BIND to do a full reload. If a DNS admin made a typo in a zone file, BIND would fail to parse that file and die. Often after hours of processing. Whomever noticed BIND wasn't running would have to read the logs, find the zone file with the error, manually review the file, fix the error, and then try starting BIND back up. Once up, the changes could propagate to the DNS slaves via zone transfers. Changes often took more than 24 hours to fully propagate. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「DNS management software」の詳細全文を読む スポンサード リンク
|